Getting Acquainted with AudioCodes MIBs

AudioCodes proprietary MIBs are located in the AudioCodes subtree (OID 1.3.6.1.4.1.5003). A classification within the subtree separates the MIBs according to the following:

■

Configuration and status MIBs – in the acBoardMibs subtree. The different MIB modules are grouped according to different virtual modules of the device. In general, the division is as follows (a more detailed breakdown of the MIBs is discussed below):

●

acBoard MIB: proprietary traps.

●

acGateway MIB: SIP control protocol specific objects. This MIB’s structure is unlike the other configuration and status MIBs.

●

acMedia MIB: DSP and media related objects. This MIB includes the configuration and status of DSP, voice, modem, fax, RTP/RTCP related objects.

●

acControl MIB: mostly MEGACO and MGCP CP related objects. A number of objects are also related to SIP. The MIB is divided into subtrees that are common to both MEGACO and MGCP (amongst these are also the SIP relevant objects) and subtrees that are specific to the different CPs.

●

acAnalog MIB: all objects in this MIB are related only to the configuration, status and line testing or resetting of analog interfaces..

●

acPSTN MIB: configuration and status of trunk related objects only. Most of the MIB objects are trunk specific. .

●

acSystem MIB: configuration and status of a wide range of general objects along with chassis related objects and a variety of actions that can be instigated.

■

Performance monitoring MIBs – in the acPerformance subtree. The different MIB modules are grouped according to different virtual modules of the device. In general, the division is as follows (a more detailed breakdown of the MIBs is discussed below):

●

acPMMedia, acPMControl, acPMAnalog, acPMPSTN, acPMSystem: module specific parameters performance monitoring MIBs

●

acPMMediaServer MIB: performance monitoring specifically for MediaServer related parameters (IVR, BCT, Conference and Trunk-Testing)

●

acPerfH323SIPGateway MIB: performance specific for SIP CP devices. This MIB’s structure is unlike the other performance monitoring MIBs.

■

Proprietary Carrier Grade Alarm MIB – in the acFault subtree:

●

acAlarm: a proprietary simplification of the standard notificationLogMIB and alarmMIB (both are also supported)

The structure of the different MIBs is similar, depending on the subtree in which they reside. The MIBs in the acBoardMibs subtree have a very similar structure (except the acBoard and acGateway MIBs). Each MIB can be made up of four major subtrees:

■

Configuration subtree: mostly read-write objects, tables and scalars. The relevant module’s configuration is done via these objects.

■

Status subtree: read-only objects, tables and scalars. Module status is collected by these objects.

■

Action subtree: read-write objects that are used to instigate actions on the device (such as restart, save configuration, and so on) and read-only objects used to receive the actions’ results.

■

Chassis subtree (in acSystem MIB only): read-write and read-only objects related to chassis control and management (this includes, fan trays, power supply modules, PSTN IF modules, etc’).

The acBoard MIB contains some deprecated objects and current proprietary trap definitions.

The acGateway MIB contains only the configuration subtree which in return is divided into common, SIP and H323 subtrees. The H323 subtree is mostly deprecated or obsolete.